Skip to content

Conversation

LVerneyEC
Copy link

@LVerneyEC LVerneyEC commented Jul 11, 2025

Hey,

This is a follow-up of #1144 as discussed there.

This PR makes the fullDomFetcher configurable through environment variables to support a wider range of setups:

  • Add support for proxy
  • Sandboxing can be disabled through environment variables (which is required by some Docker setups - e.g. AWS Fargate)
  • Disabling headless mode can be done through environment variables (which might be useful for some visual debugging of declarations or for additional stealth).

Thanks

Add support for proxy, disabling the sandboxing (which is required by
some Docker setups) and disabling headless mode in the fullDomFetcher.
Copy link
Member

@Ndpnt Ndpnt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the work on this.
However, look at my comments, but it seems to me that the core issue hasn't been fully addressed.
Could you update the PR to include this, or let me know if I’m misunderstanding something.

@LVerneyEC
Copy link
Author

Updated logic has been implemented in the latest commits and replicated into htmlonlyfetcher as well.

@Ndpnt
Copy link
Member

Ndpnt commented Sep 10, 2025

Hi @LVerneyEC,

I went ahead and refactored some parts of the code and moved the proxy credentials into the browser object instead of keeping them in the module. Since I’m a bit tied up at the moment, it was quicker to implement than to explain.
I haven’t had a chance to test it yet — could you run it on your end and confirm that everything still works?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants